-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
per_disc option for the ReplayGain plugin #3137
Conversation
It would be great if someone could test if the audiotools backend still works after these changes. I haven't got that backend to work on my system so haven't tested it myself. |
Nice! This looks great already. If we can confirm that the audiotools backend still works, I think we should merge! |
Okay, I tried to get the python audio tools backend to work again. However i noticed that I get the same error in the master branch. I don't know if I'm doing anything wrong or if this is a bug. I've used my changes without problems using the bs1770gain backend. Should I create a bug or am I doing something obviously wrong? command: beet replaygain --force system: Arch Linux audiotools-config: extraction arguments Format : %(track_number)2.2d - %(track_name)s.%(suffix)s ID3 arguments CD lookup arguments
system arguments beets config: replaygain: |
And the error: |
Aha! If this is broken on master, it's probably just a bug (or, more accurately, an API change in the library we're invoking). If this seems to work otherwise, I think it's ready to merge—and we can talk about fixing the error in a separate issue. |
Nice! I have used it frequently and it has worked well for me. I have created an issue at #3305 for the audiotools error. |
Awesome! Thank you for your help with this!!! 🚀 ✨ |
Should solve issue #293.
I'm unsure if these changes makes the rg_album_gain and rg_album_peak fields on the album level redundant. I've left it as is for now.